Skip to main content
Version: 5.1.0.0

Message mappings

Concept​

Message mappings describe the mapping of a message with a given structure to another message having another structure. Both, the structure of the source message as well as the structure of the target message are defined by Message types.

Basically there are three different types of mappings:

  • Graphical mappings describe the mapping of the source to the target structure using a graphical editor. In other words, Graphical mappings are declarative mappings. The so called IDOC mapping and Target only mapping are special types of graphical mappings.

  • XSLT mappings describe the mapping of the source to the target structure with an XSLT script. XSLT mappings are mappings using the programming language XSLT which is explicitly designed for mappings.

  • Procedural mappings, in contrast to graphical mappings, define the creation of the target message by a procedure written in a programming language. In Orchestra we use the so called XJava mapping or a JSON mapping. Both use Java to describe the mapping procedure; in the first case you may embed XPath expressions to access the content of structured messages, in the second case you use JsonPath expressions to access the content of native JSON messages. Orchestra uses a preprocessor to create plain Java code from the mapping procedure.

Note: For historical reasons there still exists a Java mapping to define a mapping but it is no more in use.

Configuration​

To configure the mapping, select an entry from the left panel. The corresponding editor will appear on the right panel. See the description of the different mapping types for details.

To use a mapping in Process models select it from the left panel, then drag the mouse into the drawing area of the process model editor and click again.